home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
iBrowse Update Disc
/
iBrowse Update Disc.iso
/
distrib
/
man
/
Manuals
/
Omniclient
/
2_useomni
< prev
next >
Wrap
Text File
|
1998-02-04
|
28KB
|
626 lines
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>Using Acorn OmniClient</TITLE>
<META NAME="GENERATOR" CONTENT="Internet Assistant for Microsoft Word 2.04z">
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<P>
<A HREF="1_intro"><IMG SRC="pics/PREV.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="Front"><IMG SRC="pics/FRONT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="TOC"><IMG SRC="pics/CONTS.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="index"><IMG SRC="pics/INDEX.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="3_BootNet"><IMG SRC="pics/NEXT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<P>
<H1>2 Using Acorn OmniClient</H1>
<HR>
<P>
This chapter describes how to load Acorn OmniClient, display and
mount file servers, and configure OmniClient for your own use.
<P>
OmniClient can either be soft-loaded from a hard disc, floppy
disc or network mount, or loaded from your Ethernet card.
<H2><A NAME="Load">Load</A>ing Acorn OmniClient from a disc or
network</H2>
<OL>
<LI>Copy !Omni, !Internet! and !InetSetup to your hard disc, or,
if you don't have one, to the network hard disc where your boot
files are kept. (Note that for discless machines, you will only be able to load
this software from servers for which there are protocol modules
resident in the machine. All machines support Level 4, those fitted
with Acorn Access may additionally load from shared Access discs.
The Appendix <A HREF="10_AppxD">OmniClient and discless workstations</A>
gives you information on how to do this.)
<LI>Run the application !OmniSetup to configure the protocols
you wish to use. Alternatively, ensure that the OmniClient Startup
file (by default located in !Omni.Files) is configured so that
only the network filing systems available on your machine are
enabled (comments in this file will help you do this).
<LI>Return your computer to its power-on configuration, by resetting
it. Find the !Omni application and double-click on it to load
it onto your icon bar. Save a Desktop boot file: if you have a
hard disc, save it to your root directory, or to !Boot with RISC
OS 3 versions 3.5 and later; if not, to the network hard disc
where your Desktop boot files are kept.
</OL>
<P>
OmniClient will now be loaded on your icon bar when you switch
on your computer.
<H2>Loading OmniClient from <A NAME="ROM">ROM</A></H2>
<P>
You may wish to upgrade the ROM on your Ethernet card to one that
includes the OmniClient software, especially if you have a site
that only has Lan Manager style servers. Please refer to your
network card supplier for details on how to make this upgrade.
<P>
When LanManFS is present in ROM, it is possible to boot resources
and the `front end' of the OmniClient application from this server.
<P>
To do this, you need to direct the client station to the required
`boot' server. You will need to configure the client by using
the following commands:
<P>
<TT><FONT FACE="Courier">*Configure fs myfileserver<BR>
*Configure filesystem LanMan<BR>
*Configure boot</FONT></TT>
<P>
This will tell the client to authenticate as user Armboot in domain
`myfileserver', then mount the Armboot share and run the !Armboot
file that it may find there.
<H2><A NAME="Using">Using</A> Acorn OmniClient</H2>
<H3><A NAME="Display">Display</A>ing available servers </H3>
<P>
Click on the OmniClient icon displayed on the lefthand side of
your icon bar <IMG SRC="pics/NETIC.GIF" HEIGHT="47" WIDTH="25">
<BR>
(or choose <B>FS list</B> from the OmniClient icon bar icon menu).
<P>
A window will be displayed, listing all the file servers and shared
discs which you can access:
<P>
<IMG SRC="pics/SERVER.GIF" HEIGHT="421" WIDTH="546">
<P>
The network filing system to which each server belongs is indicated
by a triangle on the server icon, with the following <A NAME="colour">colour</A>-coding:
<BR>
<P>
<TABLE BORDER="1">
<TR><TD WIDTH=378><B>Filing system</B></TD><TD WIDTH=236><B>Colour code</B>
</TD></TR>
<TR><TD WIDTH=378>Acorn NFS</TD><TD WIDTH=236>dark blue</TD></TR>
<TR><TD WIDTH=378>Lan Manager/NT Server (and all other Microsoft options)
</TD><TD WIDTH=236>light blue</TD></TR>
<TR><TD WIDTH=378>Lan Manager (Domain Logon)</TD><TD WIDTH=236>light blue with + sign
</TD></TR>
<TR><TD WIDTH=378>Level 4</TD><TD WIDTH=236>yellow</TD></TR>
<TR><TD WIDTH=378>Acorn Access</TD><TD WIDTH=236>green</TD></TR>
<TR><TD WIDTH=378>Acorn Access+</TD><TD WIDTH=236>green (with a plus sign)
</TD></TR>
</TABLE>
<P>
<H4>Displaying the list of file servers by name or by <A NAME="proto">proto</A>col
</H4>
<P>
The Filer menu on the file server window allows you the normal
display choices of <B>Large icons</B> and <B>Small icons</B>,
as well as a <B>Full Info</B> display which contains more detailed
information about each type of server. It also allows you to sort
the servers by server name or protocol.
<P>
<IMG SRC="pics/DISPL1.GIF" HEIGHT="65" WIDTH="138"><IMG SRC="pics/DISPL2.GIF" HEIGHT="143" WIDTH="139">
<H3>Mounting different server types</H3>
<P>
Some network fileservers combine the act of authentication and
mounting a particular directory; for example Level4 and NFS. Others,
such as Access+ and Lan Manager servers keep these two operations
separate - users are invited to authenticate themselves to the
network system before mounting any directories to which they are
allowed access.
<P>
If you are using Access+ or LanMan, you will see `dummy' fileservers
called Access+ and LanManager in the list of fileservers window.
You may authenticate yourself by clicking on these icons and entering
the log-on details in the dialogue box displayed. Once authenticated,
network mounts can be selected simply by selecting them from the
list of fileservers window.
<P>
If a `home' directory is defined for you on an NT/Lan Manager
server, this will be mounted with the name `Home'.
<H3>Primary domain controllers</H3>
<P>
If you are using NT Servers, such as the Acorn School Server or
Class Server products, you should have set up one server (if you
have more than one) as a primary domain controller. This means
that you need only authenticate once to have all the resources
allocated to you in that domain available for your use. This is
a natural consequence of the security model implemented in a Microsoft
domain environment.
<P>
<IMG SRC="pics/LMLOG.GIF" HEIGHT="322" WIDTH="401">
<H3>Mounting a file server</H3>
<P>
There are several different ways to mount a file server:
<UL>
<LI>by clicking on a file server icon in the list of file servers
<LI>by choosing a pre-saved file server from the icon bar icon
menu
<LI>by filling in a Mount dialogue box from the icon bar Mounts
menu (this is for file servers which do not appear on the list
of file servers)
</UL>
<H4>Mounting a file server from the <A NAME="list">list</A> of
file servers</H4>
<P>
To connect to a particular server, double-click on its icon; you
will be connected directly with the server if all relevant information
is available, otherwise a Mount dialogue box will be displayed:
<P>
<IMG SRC="pics/MOUNT1.GIF" HEIGHT="338" WIDTH="517">
<P>
Where mounts have previously been saved (see <A HREF="#mounts">Mounts file</A>)
their details will already be entered in the Mount box, so all
you will have to enter is the password.
<H4>Mounting a pre-saved file server from the <A NAME="icon">icon</A>
bar icon menu</H4>
<P>
If you have already mounted a file server, or saved the details
of a mount in the Mounts file (see <A HREF="#mounts">Mounts file</A>)
then you can go to the <B>Mounts</B> submenu to display the (partially)
completed dialogue box for that mount. This enables easy access
to regularly accessed fileservers.
<P>
For example:
<P>
<IMG SRC="pics/IBMOUN.GIF" HEIGHT="490" WIDTH="462">
<P>
If you choose the <B>Delete</B> option, this mount is deleted
from the mounts file if you then choose <B>Save mounts</B> from
the <B>Mounts</B> sub-menu.
<H4>Mounting a file server which is <A NAME="not">not</A> displayed
on the list of file servers</H4>
<P>
If you need to mount a file server that is not displayed in the
list of file servers, you can go to the <B>Protocols</B> submenu
and click on one of the available protocols displayed. A dialogue
box will then appear (with a default user) enabling you to enter
all the necessary details before attempting to mount the file
server.
<P>
For example:
<P>
<IMG SRC="pics/L4MOUN.GIF" HEIGHT="215" WIDTH="312"><BR>
<P>
<IMG SRC="pics/LMMNT.GIF" HEIGHT="215" WIDTH="314"><BR>
<P>
<IMG SRC="pics/ACCPLU.GIF" HEIGHT="139" WIDTH="301"><BR>
<H4>Mounting a file server <A NAME="auto">auto</A>matically</H4>
<P>
You can mount file servers automatically from the OmniClient command
tail in your Desktop boot file. For example:
<P>
<TT><FONT FACE="Courier">Run ADFS::4.$.!Omni mount1 mount2 mount3</FONT></TT>
<P>
See <A HREF="#dtboot">Running OmniClient from your Desktop boot file</A>.
<P>
When the OmniClient application is started each mount name is
looked for in the mounts file (see <A HREF="#mounts">Mounts file</A>).
If the mount is with a filing system (or server) that needs no
password (e.g. Acorn Access), or if the password is in the mounts
file, the mount will be accessed immediately and an icon will
appear on the icon bar.
<P>
If the mount requires a password a Mount dialogue box is displayed
for you to fill in.
<H4>Using mount <A NAME="alias">alias</A>es</H4>
<P>
A mount alias is the name that appears under a mounted server
icon on your icon bar. It is defined in the <B>Name</B> field
of the <B>Mount server</B> dialogue box.
<P>
You can either use the default alias, if applicable, or choose
your own alias for a given mount (to aid you, OmniClient suggests
a default alias name where it can, by choosing the `short form'
of the server name, as shown in the list of file servers). If
a mount (either connected or in the saved mounts file) already
exists with this name, the mount alias field is left empty for
you to fill in yourself.
<P>
Each mount must have a unique alias, for all protocols. If you
don't choose a unique mount name when you log on to an OmniClient
supported server, an error will be generated asking you to choose
another name.
<H3>After you have mounted a file server</H3>
<P>
When you have successfully logged on to a file server, an OmniClient
icon with the name (i.e. the mount alias) of the new mount will
appear on the icon bar, and the directory display for the root
of the mount will be opened on the desktop, if you have requested
it by choosing <B>Open</B>.
<H4><A NAME="Displ">Displ</A>aying available servers</H4>
<P>
After you have established a mount, and an OmniClient icon with
the name of the new mount has appeared on the icon bar, clicking
Select on this icon will not display the list of file servers,
but instead will display the directory mounted by that icon.
<P>
To display the list of available servers you must either choose
<B>FS list</B> from the OmniClient icon bar icon menu, or click
Adjust (not Select) on the OmniClient icon.
<H4>Windows NT Server</H4>
<P>
OmniClient allows Acorn platforms to achieve high performance
connectivity in conjunction with the Windows NT Server product.
Acorn clients will appear to the administrator in a very similar
fashion to Windows or MS DOS users. The example below shows an
active connection from an Acorn Risc PC to the a server:
<P>
<IMG SRC="pics/CONN1.GIF" HEIGHT="406" WIDTH="640">
<P>
The following example of File Manager running on a Windows
NT Server, shows how RISC OS files can be stored and retrieved
as users on the Local Area Network require them.
<P>
<IMG SRC="pics/MARK2.GIF" HEIGHT="480" WIDTH="640">
<P>
The Windows NT Server environment also allows the OmniClient
application to choose file servers when storing and retrieving
remote files. This means that where more than one file server
exists the system can be made totally flexible.
<H3>Running OmniClient from your Desktop <A NAME="dtboot">boot
file</A></H3>
<P>
If you set up OmniClient to run from your Desktop boot file, you
can add one or more mount aliases to the command tail (the command
tail is any additional text you add after the command to run !OmniClient)
these will then be mounted automatically (although you may have
to supply passwords for the mounts if these are not specified
in the mounts file).
<P>
Instead of adding a list of mount aliases to the OmniClient command
tail, you can just add -ALL, in which case OmniClient will behave
as if the command tail listed all the mounts in the mounts file.
<P>
By specifying the fileserver type in the command tail (for example
Share+, LanMan+ etc.) all the fileservers of this type will be
automatically mounted. A dialogue box will be displayed if more
information (for example a password) is required.
<P>
To support multiple saved mounts files (e.g. master network file
for booting, and a writable per-user mounts file), a *command
OmniLoadMounts lets a named mounts file be loaded (merged with
those already in memory). Mounts will always be saved to the mounts
file Omni$Path Mounts unless a mount has the LOCKED flag set (see
<A HREF="#flags">Flags in the mount file</A>).
<H3>Other options on the icon bar icon menu</H3>
<H4>Getting information about a mount</H4>
<P>
<B>About</B> displays the mounts name, server name, directory
path, user name and authenticator:
<P>
<IMG SRC="pics/ABOUT.GIF" HEIGHT="216" WIDTH="444">
<P>
The `authenticator' is required by NFS servers who may have a
separate name server machine.
<H4>Opening a root directory</H4>
<P>
<A NAME="Open"><B>Open `$'</B> opens the user root directory of
the file server you are on.</A>
<H4><A NAME="Dismount">Dismount</A>ing a mount</H4>
<P>
<B>Dismount</B> dismounts the file server and closes any associated
directory displays.
<H4>Finding the free space on a mount</H4>
<P>
<B>Free</B> opens a dialogue box that shows you the amount of
free space on a mount:
<P>
<TABLE >
<TR><TD ALIGN="LEFT" VALIGN="BOTTOM" WIDTH=111><B><IMG SRC="pics/FREE1.GIF" HEIGHT="175" WIDTH="97"></B>
</TD><TD ALIGN="LEFT" VALIGN="BOTTOM" WIDTH=161>
<OL>
<LI>Choose <B>Free</B>
<LI>Dialogue box appears
</OL>
</TD><TD ALIGN="LEFT" VALIGN="BOTTOM" WIDTH=319><B><IMG SRC="pics/FREE2.GIF" HEIGHT="103" WIDTH="309"></B>
</TD></TR>
</TABLE>
<P>
<B>Bye</B> dismounts all active connections and log off all network
domains. A confirm box is displayed before this takes place.
<H4><A NAME="Quit">Quit</A>ting OmniClient</H4>
<P>
To quit OmniClient, click on the Task manager icon on the icon
bar to display the Tasks window, click Menu over the OmniClient
entry and choose <B>Task/Quit</B>.
<H2>Mounts <A NAME="mounts">file</A></H2>
<P>
Although it is not necessary to access this file under normal
circumstances, the mounts file contains the details of any mounts
you have specified. The file is in !Omni.Files.Mounts.
<P>
To save one or more mounts choose <B>Save mounts</B> from the
<B>Mounts</B> submenu. This saves the details of any mounts you
have specified to the mounts file.
<P>
Each line of the mounts file contains information for a mount.
Usually this will be all the information needed to connect a mount
with the exception of the user's password, although this can be
supplied if the user feels it is not a security problem.
<P>
The fields on each line are separated by a comma and white space
of any sort other than a new line. The trailing fields on a line
may be left off if the null string is to be used. Any line beginning
with a `#' character is ignored (and will be lost if the file
is rewritten).
<P>
Below is an example mounts file:
<P>
<TT><FONT FACE="Courier"># > <Omni$Path>Mounts <BR>
# Mount list saved by OmniClient at 16:14:54 on 8 Nov 1994 <BR>
# <BR>
# Protocol, Alias, Flags, Server, Mount path, User ID, <BR>
# Password, Authentication <BR>
# <BR>
LanMan,IanC,L,PC1,C:,ian<BR>
LanMan,PC2,L,PC2,,ian <BR>
NFS,Apps,P,zebedee,/extra/apps,apps,letmein,zebedee</FONT></TT>
<P>
In the previous example the mount called Apps could be mounted
without typing a password (it has the one it needs). Also, note
that Access does not require a password or authenticator to gain
access to a hard disc or CD ROM.
<P>
A null password can be represented in the mounts file as the string
"" (i.e. two double-quotes without any spaces). This
could be used where a guest account has no password, and the user
doesn't wish to be prompted for a password to be entered. However,
in the case of ShareFS, they are automatically assumed.
<P>
The mounts file is automatically updated when you choose <B>Save
mounts</B> from the Mounts submenu. This also remembers the state
of the <B>Open</B> button.
<H4>Flags in the mount <A NAME="flags">file</A></H4>
<P>
Extra flags are set from the flags field:
<P>
<TABLE >
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=64>L</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=170>LOCKED
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=64>H </TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=170>HIDDEN
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=64>P </TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=170>PRESET
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=64>O</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=170>OPEN
</TD></TR>
</TABLE>
<UL>
<LI>Mounts with the LOCKED flag do not get saved into the user
mounts file, and so can be used in read-only, master mounts files
used at boot time.
<LI>Mounts with the HIDDEN flag set do not appear in the mounts
list submenu, in the 'servers' window, or on the icon bar.
</UL>
<P>
The HIDDEN flag is provided to allow for 'system' mounts which
are used in a networked boot sequence (e.g. scrap area) but which
remain hidden from the user (not appearing on the icon bar, etc).
In conjunction with the LOCKED flag for master mounts file(s),
you can setup a very flexible boot sequence that has its complexity
hidden from the end user. Note that the HIDDEN flag will not prevent
servers/mounts appearing in the 'servers' window that have been
auto-located by a network scan (if this is enabled see <A HREF="#appconfig">Application configuration</A>).
<UL>
<LI>The PRESET flag allows extra servers/mounts to be presented
in the network servers window - perhaps non-local servers which
protocols cannot automatically scan for. Mount file entries with
the PRESET flag set do not appear in the mounts list submenu unless
they are currently connected. This flag has a higher priority
than HIDDEN, and mounts file entries that mistakenly have both
set will be treated as PRESET.
<LI>Mounts with the OPEN flag set do not open directory displays
when they are mounted - i.e. if the flag is not set the action
is to open the window automatically, thus making this version
compatible with Release 1. The default action is to set the flag
for new mounts.
</UL>
<P>
To set these flags, you must edit the mounts file to include the
strings L, P,O or H flags field.
<P>
Note that PRESET and HIDDEN are mutually exclusive, since the
purpose of PRESET is to have mounts that cannot be located automatically
(for whatever reason) appear in the servers window, and the purpose
of HIDDEN is to stop them appearing.
<H2>Omni<A NAME="Setup">Setup</A></H2>
<P>
This application gives the network manager an easy way of selecting
which network protocols are in use. Note that a choice has to
be made between NetBEUI and IP for Lan Manager access. The option
to switch on the display of all network servers is also available,
as well as the options given below. See also <A HREF="9_AppxC#LTrans" >*Configure LanManTransport</A>
and *<A HREF="9_AppxC#conFS">Configure FS</A>.
<H2>Application <A NAME="appconfig">configuration</A></H2>
<P>
To allow configuration to be stored on a per-user basis, all configuration
files used by the OmniClient application are accessed through
the system variable Omni$Path (by default set to <TT><FONT FACE="Courier">!Omni.Files</FONT></TT> ).
This directory contains three files:
<UL>
<LI><TT><FONT FACE="Courier">Mounts</FONT></TT> (see <A HREF="#mounts">Mounts file</A>)
<LI><TT><FONT FACE="Courier">Extensions</FONT></TT> (contains
the Filetype extension mappings list)
<LI><TT><FONT FACE="Courier">Startup</FONT></TT> (obey file).
</UL>
<P>
The Startup obey file is executed when the application is loaded,
and may contain commands to load protocol modules, set Omni$User
variables, etc. It can also set the system variable Omni$Options
which allows the default configuration of the application in a
similar manner to that of Acorn !Edit and Edit$Options. Currently
defined options are:
<P>
<TABLE >
<TR><TD WIDTH=92><B>Option</B></TD><TD WIDTH=255><B>Action</B>
</TD><TD WIDTH=221></TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=92><TT><FONT FACE="Courier">s<I>N</I></FONT></TT>
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=255>Sort type</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=221>N = 0 (None)
<BR>
N = 1 (Name)<BR>
N = 2 (Protocol/Name)
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=92><TT><FONT FACE="Courier">sd<I>N</I></FONT></TT>
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=255>Display type</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=221>N = 0 (Large icons)
<BR>
N = 1 (Small icons)<BR>
N = 2 (Full info)
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=92><TT><FONT FACE="Courier">a</FONT></TT>
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=255>Auto-location of network servers ON
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=221></TD></TR>
</TABLE>
<P>
This is primarily for further reading because the Sort type, Display
type and Auto-location of network servers options can be modified
in !Omni.Files.Startup. However running !OmniSetup will display
these options in a dialogue box permitting a more efficient selection
procedure, but the option is still there to modify your choices
as you wish.
<P>
The <TT><FONT FACE="Courier">a</FONT></TT> option allows the OmniClient
software to scan the network to enable the display of all network
servers. If the <TT><FONT FACE="Courier">a</FONT></TT> option
is not present, only those mounts that are specified in the Mounts
file will be displayed.
<P>
For example:
<P>
<TT><FONT FACE="Courier">Set Omni$Options s0 d1<BR>
Set Omni$Options a s0 d1</FONT></TT>
<P>
You may wish to edit the Startup file to comment out protocol
modules that are not required, or alter the Omni$Options settings,
but it is recommended that you use !OmniSetup to do this.
<H4>Setting the <A NAME="user">user </A>name</H4>
<P>
You can use the system variable Omni$UserFilingSystem to set the
value of the user name. If the variable is not set but Omni$User
is set then the value of this will be used as the default user
name. This should ensure that in general on a user's private machine
only the password need be typed.
<P>
For example:
<P>
<TT><FONT FACE="Courier">Omni$UserNFS JSmith</FONT></TT>
<H2><A NAME="Printing">Printing</A> using OmniPrint</H2>
<P>
You can use Acorn's standard version of !Printers to access remote
printers located or controlled by NT or other Lan Manager-type
network printers, or any other network printer type supported.
<UL>
<LI>Click Menu over the Printer control window and choose the
<B>Connection...</B> option. This displays the Connections window.
<LI>Click on the <B>File</B> option.
<LI>Enter a filename of the following form:
</UL>
<P>
<TT><FONT FACE="Courier">OmniPrint<I>#FSName;Server;Printer;User;Password;Options;Size:</I></FONT></TT>
<UL>
<LI>Save the new !Printers configuration.
</UL>
<P>
The fields you must fill in are the FSName, Server and Printer
names, although the latter two may be the same for some situations
(e.g. a stand-alone AUN printer). Note that User, Password, Options
and Size are all optional fields. The file name must be terminated
by a colon.
<P>
Any filename given is ignored - the critical data is contained
in the special field. Fields are semi-colon separated, and illegal
(RISC OS) characters should be encoded as follows:
<P>
<TABLE >
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>RISC OS character</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>encoding characters</B>
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161>SPACE</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265>~_ (underscore)
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>"</B></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>~'</B>
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>| </B>(solidus)
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>~l</B> (lowercase L)
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>:</B></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>~1</B> (numeric one)
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>; </B></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>~!</B>
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>, </B></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>~.</B>
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=161><B>~</B></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=265><B>~~</B>
</TD></TR>
</TABLE>
<P>
Examples:
<P>
<TT><FONT FACE="Courier">OmniPrint#NFS;ant;lp;nas:<BR>
OmniPrint#LanMan;NTserver;NTprint;guest;guest:</FONT></TT>
<P>
For protocols that require the file size prior to the transmission
of any data, an optional field Size can be included in the special
field (none of the protocols in this release need the size field).
<H3>Alternative <A NAME="print">print</A>ing using NFS</H3>
<P>
You can also use NFS software in conjunction with the standard
RISC OS Printers application to send print jobs to printers connected
to remote NFS servers.
<H4>Loading the NFS software</H4>
<P>
Obviously the Printers application needs to use NFS software to
send the print job to an NFS server. You should ensure that OmniClient
is set up to use NFS before you run the Printers application.
<H4>Setting up the Printers application</H4>
<P>
Set up the printer in the same way as any other (see the chapter
on setting up printers in the RISC OS 3 User Guide) except for
the <B>Connections</B> window, where you should choose <B>NFS</B>
and type in some information:
<P>
<IMG SRC="pics/CONN3.GIF" HEIGHT="483" WIDTH="334">
<UL>
<LI>The Server must be running a utility known as the <A NAME="pcnfsd">pcnfsd</A>
daemon. You need this same utility to use the server as a name
server, so:
<LI>Any server you can use as a name server you can also use as
a print server, and vice versa.
<LI>The Printer must be the name of a printer that the server
can access. If you don't give a printer name, the server will
use the printer named lp - the default name for a UNIX printer.
<LI>The Username gets passed to the program that does the printing
(lpr in the case of UNIX), and is used to establish your access
rights to the printer. If you leave this out the server uses a
blank user name; you can do so if there are no restrictions on
printer use at your site.
<LI>The Options also get passed to the program that does the printing.
If you omit them, no options are forwarded.
</UL>
<P>
Don't forget to choose Save choices from the Printers icon bar
menu if you want the new setup to be saved.
<H4>Using the Printers application</H4>
<P>
Once you've got everything correctly set up and running, you can
use the Printers application just as you always have. Any files
you drop onto its icon get converted to the correct format for
the remote printer (e.g. PostScript), and then forwarded to it
via the NFS server.
<P>
<A HREF="1_intro"><IMG SRC="pics/PREV.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="Front"><IMG SRC="pics/FRONT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="TOC"><IMG SRC="pics/CONTS.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="index"><IMG SRC="pics/INDEX.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="3_BootNet"><IMG SRC="pics/NEXT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<P>
</BODY>
</HTML>